Fix CI test failure: TestFruitColourFallback in catch ruleset - #341
Conversation
…fication Agent-Logs-Url: https://github.com/winnerspiros/osu/sessions/4b89ea94-0ef4-4f3a-9dd7-ffb7cd4e8d09 Co-authored-by: winnerspiros <1675249+winnerspiros@users.noreply.github.com>
|
@copilot check ci errors and warnings and fix |
…rison Agent-Logs-Url: https://github.com/winnerspiros/osu/sessions/f3fc7ab7-91f5-4585-85c4-d37cdef778b8 Co-authored-by: winnerspiros <1675249+winnerspiros@users.noreply.github.com>
Checked CI logs for run 26102450367. Two failures found:
|
There was a problem hiding this comment.
Pull request overview
This PR fixes a flaky catch ruleset test around hyper-dash fruit colouring and includes small cleanup/migration adjustments elsewhere.
Changes:
- Retries the hyper-dash fruit colour assertion until async drawable loading completes.
- Compares sprite colour via explicit SRGB access.
- Removes an unused matchmaking field and simplifies a nullable colour assignment.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
osu.Game.Rulesets.Catch.Tests/TestSceneHyperDashColouring.cs |
Updates the fruit colour test to wait for the expected colour and compare via TopLeft.SRGB. |
osu.Game.Rulesets.Osu/Edit/OsuSliderVelocityToolboxGroup.cs |
Replaces osuTK with System.Numerics for vector usage. |
osu.Game/Screens/Edit/Components/FormSampleSet.cs |
Simplifies null-checked triangle colour assignment. |
osu.Game/Screens/OnlinePlay/Matchmaking/Queue/ScreenQueue.cs |
Removes an unused historyInsertOrder field. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| using osu.Game.Rulesets.Osu.Objects; | ||
| using osu.Game.Screens.Edit; | ||
| using osuTK; | ||
| using System.Numerics; |
Fixes the consistently-failing
TestFruitColourFallbacktest inTestSceneHyperDashColouring.Changes Made
AddAssert→AddUntilStepfor the hyper-dash fruit colour check, consistent with how the catcher colour check works. This ensures the assertion retries until async drawable loading (via[BackgroundDependencyLoader]) andLegacyCatchHitObjectPiece.LoadCompletehave completed.c.Colour == expectedColourtoc.Colour.TopLeft.SRGB == expectedColour. This uses direct SRGB field access instead of relying on the implicitColourInfo → SRGBColour → Colour4conversion chain (which internally assertsHasSingleColour = true), making the comparison more robust and consistent with the pattern used elsewhere in the codebase.Notes
DetectSdkLocationsMSBuild task, Xcode version mismatch) is a CI infrastructure issue and is not fixable in code.